feat: implement handle validation and contributor roadmap/release docs - #203
Merged
Chucks1093 merged 1 commit intoApr 26, 2026
Merged
Conversation
…ccesslayerorg#192 in one scoped update
|
@FrostGraphix Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR closes four scoped contributor tasks by adding strict creator handle validation in the contract, documenting storage intent and roadmap expectations, and adding a concise testnet release checklist for verification.
Closes #142
Closes #150
Closes #191
Closes #192
Changes proposed
What were you told to do?
Implement one grouped PR that closes four open issues: creator handle validation rules, contract storage comments, a testnet verification release checklist, and a roadmap item for optional creator profile expansion fields.
What did I do?
Creator Handle Validation (#142)
egister_creator with explicit constraints (length 3..32, allowed characters: lowercase �-z, digits